Last revision: 12/18/2018
This document contains important information about System Platform 2017 Update 3. This version of System Platform includes a number of security enhancements and new features for the component products of System Platform.
Supported System Platform Versions for Product Upgrade
You can upgrade directly to System Platform 2017 Update 3 from the following versions:
Note that all existing products must be upgraded to the same version.
Supported System Platform Versions for Migration
You can migrate user-created content (for example, .cab files, .aaPKG files, Historian databases, etc.,) to System Platform Update 3, as long as the content was created in one of the following product versions:
Server-based Licensing
System Platform 2017 Update 3 continues to utilize the server-based licensing subsystem introduced in System Platform 2017. This new licensing subsystem provides centralized license management, and replaces the file-based licensing system that was used in prior releases. Licenses must be activated before use.
If you are upgrading from Windows Server 2014 R2 SP1 (with or without patches), you must first install and configure a license server node, and activate the licenses to ensure continuous plant operation. The license server is typically installed on the Galaxy Repository node, but you can use a dedicated license server. See the "License Installation and Activation" section of the System Platform Installation Guide (WSP_Install_Guide.pdf), located at the root of the DVD.
InTouch OMI
System Platform 2017 introduced InTouch OMI, the first Operations Management Interface to leverage both Human Machine Interface (HMI) and Supervisory Control and Data Acquisition (SCADA) systems and deliver a next generation visualization experience. InTouch OMI extends traditional HMI and SCADA applications to deliver a convergence platform for both Operational Technology (OT) as well as Information Technology (IT). This update to System Platform 2017 extends the features and functionality of InTouch OMI, including the ability to use InTouch Access Anywhere to access run time applications.
One key aspect of InTouch OMI is its ability to automatically assemble applications based on a data model, resulting in minimal engineering and manageability that has not previously been available. InTouch OMI enables the first industrial application that will deliver a tailored and contemporary experience to any environment or device, including control rooms, industrial panels, desktops, laptops, tablets and phones.
A Software Development Kit (SDK) is included to allow programmatic additions to InTouch OMI. Help for the SDK can be accessed from the Start Menu, under Wonderware Documentation.
Using an Object Wizard with a Linked Symbol Wizard
InTouch OMI includes new functionality that lets you see how a symbol wizard linked to an object wizard is configured as you add it to an overview symbol or to a pane. In previous releases, only the default configuration was shown unless the symbol was contained in an overview symbol.
InTouch HMI: Using a symbol wizard linked to an object wizard is not supported in an InTouch HMI application window, either during configuration or at run time. The new functionality applies only to using an object wizard with a linked symbol wizard within an InTouch OMI pane.
Readme Files for Other Products in this Release
To access individual product Readme files, insert the System Platform installation DVD and click on the link. Review the known and resolved issues contained in each Readme file for the following component products are updated for this release:
Remote Desktop Services and InTouch HMI
When InTouch HMI 2017 Update 3 is installed on a Windows Server 2016 computer with Remote Desktop Services enabled, WindowViewer will fail to launch. WindowMaker cannot be closed unless shut down using Task Manager.
Workaround:
http://www.catalog.update.microsoft.com/Search.aspx?q=KB3194798
Important: You can install the Microsoft update before or after System Platform. However, we recommend installing the Microsoft update before you install System Platform.
Affected Systems
This information is applicable to a small subset of highly secured environments, in which operating systems and supporting networks have been configured to enable TLS 1.2 and where TLS 1.0 and 1.1 have been purposefully disabled. In these rare instances, some additional configuration is required to ensure that System Platform will work as expected.
System Platform 2017 Update 3 includes various measures to strengthen security, including the ability to leverage the latest version of transport layer security (TLS 1.2), provided that TLS 1.2 it has been enabled and configured in the host operating system.
As of the System Platform 2017 Update 3 release date, Microsoft Windows Server 2016 does not support TLS 1.2 by default. You must enable it by applying Microsoft updates and several manual edits to the system registry. The tasks of applying all Microsoft updates and editing the system registry must be completed before you install System Platform 2017 Update 3. These instructions also apply to any other software products that support TLS 1.2. Follow the instructions listed below.
If you are required to enable TLS 1.2 and disable TLS 1.0 and TLS 1.1:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
For important information about this product release, go to the AVEVA Global Customer Support (GCS) web site. Information on the GCS web site includes product requirements, compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.
System Platform 2017 Update 3 adds new product features and includes several measures to enhance security, including the secure SuiteLink connection.
Secure SuiteLink Connection
The secure SuiteLink connection, enabled with TLS 1.2 protocol, encrypts the communication channel between the SuiteLink Server and SuiteLink Client. A secure SuiteLink communication channel must establish the TLS Handshake, key exchange and server certificate validation.
The ArchestrA Service Bus (ASB) Security supports secure communication using the TLS protocol and digital certificates. Use the Configurator to configure the ASB security on every node. For more information, refer to the section, ‘Configuring ASB Security’ in the System Platform Installation Guide.
To ensure interoperability, the secure SuiteLink infrastructure continues to support and allow both secure and insecure communication. Only a secure client and a secure server will provide secure and encrypted communications. An unsecure endpoint (either client or server) prevents secure communications between the nodes.
If the authentication fails between the Client and the Server, or if the Client or Server do not have access to the Certificate store, the system continues with the unsecure and non-encrypted connection as a fallback.
For detailed information about the secure SuiteLink connection and how to configure it, see the ArchestrA Protocols Users Guide, installed on your local computer and available through the Windows Start menu. Also see the Wonderware Operations Integration - Core Communications Driver (G-3.0 Series) Help, available through the System Management Console (SMC) online help system.
Sentinel Agent and Manager
Each node contains a Sentinel Agent that constantly monitors the License Server to ensure that it is accessible. In the event that a node is unable to communicate with the License Server, the Sentinel Agent sends a message to the Sentinel Manager. The Sentinel Manager can be configured to email a warning so you can quickly fix any issues and ensure that operations are not interrupted.
Important: Please see Sentinel Installation and Configuration for important information about the sequence of Sentinel installation and configuration steps.
Introducing the AVEVA Digital Exchange
The AVEVA Digital Exchange is a new online marketplace that lets you explore products and offerings from a problem-first perspective, or from an industry/vertical perspective. You can download new InTouch OMI apps and other System Platform enhancements. A new Galaxy Import menu item has been added to the ArchestrA IDE that lets you import an app directly into your galaxy.
Security Enhancements
When Historian or Application Server Galaxy Repository is selected for installation, the Security Server component is automatically selected for installation on the node. The Security Server supports single-sign-on and provides secure, encrypted communications between nodes. This improves the overall security of System Platform against external threats, such as man-in-the-middle attacks.
To further enhance security, the ArchestrA User Account no longer requires elevated system permissions. This account is used for communication between various System Platform components.
Auto-LogOn and LogOff
New security attributes let you use configure automatic logon and logoff for ViewApps. The Windows credentials of the currently logged-in Windows user can be passed to the ViewApp, without the user having to re-enter their credentials. Users can be automatically logged off after a period of inactivity. You can configure a timer that shows the user how much time remains before they are automatically logged off.
Read-Only Option for ViewApps
ViewApps can be set at configuration time to be read-only. If set as read-only, a ViewApp can only be changed to read/write from the IDE. Users cannot change this setting while the ViewApp is running or when launching the ViewApp.
Correct Symbol Options Shown During Configuration when an Object Wizard is Linked to a Symbol Wizard
In previous releases, when an Object Wizard was used to add a symbol to an overview symbol, and the symbol included a Symbol Wizard, the symbol had to be placed in a container overview symbol or it would be shown with its default configuration, regardless of the selected settings. The need to use a container has been removed in this release. The symbol is now displayed according to its configuration. Note that this behavior change only applies to what is seen while configuring symbols. Symbols always displayed correctly at run time.
A symbol wizard linked to an object wizard in an InTouch application window will not show the correct settings during configuration or at run time. The new behavior only applies to adding linked symbols to an InTouch OMI pane.
Ability to Set Owning Object in Multi-Galaxy Environments with the Graphic Editor
To simplify setting the owning object in multi-galaxy environments, you can now include the galaxy name from within the Graphic Editor. Previously, scripting was needed to set the owning object in multi-galaxy environments.
Support for Touch Gestures in InTouch OMI Apps
Support has been added for touch and associated gestures within InTouch OMI apps. Some InTouch OMI components, such as the search textbox and NavTree, have touch already enabled. You can configure your ViewApps to respond to touch to simplify user interactions during run time. You can also build your own touch-enabled apps through the InTouch OMI SDK.
Utilize InTouch Access Anywhere to Execute InTouch OMI ViewApps
In addition to executing legacy InTouch HMI applications, InTouch Access Anywhere now lets you execute InTouch OMI ViewApps. Enjoy the same mobility and utility that InTouch Access Anywhere provides for your legacy applications with InTouch OMI ViewApps.
Embedded Search in the Navigation Tree
You can allow your run-time users to search the navigation tree (NavTree) to quickly find items within the tree. Just enter a search term in the search bar, and immediately navigate to the item you are looking for. The search bar can be disabled, if preferred.
AlarmApp Allows Live and Historical Content to be Filtered by Area
The InTouch OMI Alarm App now allows users to filter content by area, for both live and historical data. This exposes the area model to users so they can select any node to see the alarm grid view.
AlarmApp Gives Users Access to Properties in the Alarm Grid
The properties available in the ArchestrA Alarm Control can be accessed with the InTouch OMI App. Some of the properties that can now be configured and used include Alarm Query, Asset Browser, Context Menus, as well as parameters for controlling the appearance of the grid.
AlarmApp Automatically Sets the Current Area or Asset at Run Time
At design time, an application engineer can configure the InTouch OMI Alarm App to automatically show alarms from either the current area or the current asset, based on what has been selected in the navigation pane. The alarm query of the AlarmApp can then determine which alarms should be displayed.
Programmatic Alarm Acknowledgement
A button can be added to a ViewApp to allow users to quickly respond to alarm states. Users can be given the ability to acknowledge, silence, enable/disable, and other interactions, such as Acknowledge with just the push of a button.
Historian Client App Can Load Pens
As users navigate through the system, they can now load pens associated with different objects. This allows them to view trends for a selected asset, through the InTouch OMI Historian Client App.
Hyperlink Animation and Hyperlink Script Function
Support has been added to the graphic library to allow InTouch OMI ViewApps to utilize hyperlink animation and the hyperlink script function.
Halo Animation to Show Current Focus in ViewApps
Halo animation can be configured to appear when the user places a mouse cursor directly over a graphic element while a ViewApp is running. The halo highlights the current interaction focus within a ViewApp.The halo follows the boundary of the graphic element, which is configured with any user interaction animation.
Configurable Center Point for ViewApp Zoom
Specific areas of symbols shown in a running ViewApp can be zoomed in to show more detail. Instead of focusing on the center point of the pane when zooming in, the center point of the zoom area can be specified in a script. The ability to place the zoom area center point anywhere within the boundaries of a symbol lets you set which specific portion of the symbol to show more detail.
Link to External Content
Support has been added for external content that you have developed outside of System Platform. You can now link to this content and display the linked content within an InTouch OMI viewer app.
Support for Advanced Numeric Formatting
Advanced numeric formatting styles that were developed for InTouch HMI applications are now supported in InTouch OMI ViewApps. Applications and graphics that leverage advanced numeric formatting will automatically update during run time, whenever the galaxy configuration is changed.
InTouch HMI 2017 Update 3 provides support for the latest versions of Microsoft products and includes several new features. Refer to the GCS Technology Matrix for the list of supported Microsoft products. The following section summarizes the major features introduced in InTouch HMI 2017 Update 3.
Enhanced Security of Alarm DB Utilities and Controls
The following InTouch Alarm DB utilities now support TLS 1.2 protocol and includes other enhanced security enhancements:
The following InTouch Alarm Controls now support TLS 1.2 protocol and includes other enhanced security enhancements:
InTouch Web Client Enhancements
There are major improvements in the InTouch Web Client since the InTouch HMI 2017 Update 2 release.
Trend Pen Supports Historical Data
The Trend pen symbol now supports:
Hyperlink Animation for ArchestrA Graphics
A new animation that allows you to launch a browser with a configurable URL.
FillColor Support for Area under the Trend Pen Curve
You can use the standard FillColor property to fill the area under the Trend Pen curve in design and runtime.
Touch Support for Native Push Button Animation
The Push down animation in InTouch HMI standalone applications now support the touch gestures for touch enabled devices.
InSight Publisher is now available as part of InTouch WindowMaker and Application Manager
You can now launch InSight Publisher from Application Manager and WindowMaker. You can also publish applications to InSight servers provided InSight is configured and licensed.
Modeless Cross Reference dialog box
The cross reference dialog box is now modeless allowing you to use other functionalities of InTouch WindowMaker while the cross reference dialog box is open.
Secure SuiteLink Connection
The secure SuiteLink connection, enabled with TLS 1.2 protocol, encrypts the communication channel between the SuiteLink Server and SuiteLink Client. A secure SuiteLink communication channel must establish the TLS Handshake, key exchange and server certificate validation.
The ArchestrA Service Bus (ASB) Security supports secure communication using the TLS protocol and digital certificates. Use the Configurator to configure the ASB security on every node. For more information, refer to the section, ‘Configuring ASB Security’ in the System Platform Installation Guide.
To ensure interoperability, the secure SuiteLink infrastructure continues to support and allow both encrypted and non-encrypted communication. Only a secure client and a secure server will provide secure and encrypted communications. An unsecure endpoint (either client or server) prevents secure communications between the nodes.
If the authentication fails between the Client and the Server, or if the Client or Server do not have access to the Certificate store, the system continues with the unsecure and non-encrypted connection as a fallback.
For detailed information about the secure SuiteLink connection and how to configure it, see the ArchestrA Protocols Users Guide, installed on your local computer and available through the Windows Start menu. Also see the Wonderware Operations Integration - Core Communications Driver (G-3.0 Series) Help, available through the System Management Console (SMC) online help system.
The Wonderware Historian 2017 Update 3 (version 17.3.000) includes these features:
Web Help - Browser-based User Assistance
Web help components have been delivered in this release. Web help opens in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation and tutorial videos.
Typically, help content is installed on your local machine as part of the documentation library, and displays in your browser without requiring an Internet connection. To open the help, use one of the following methods (depending on the editor/UI you are using):
C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\NGX\index.htm
Browser Requirements and Recommendations
Internet Explorer is recommended. You can also view web help Firefox. If you use Firefox, you may need to install and use an IE rendering extension (for example, IE Tab) to ensure that video content is shown.
Browser Permissions for Displaying Web Help
Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.
You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the "Allow active content to run in files on My Computer." Permissions and security settings will vary depending on your specific browser.
Playback of Tutorial Videos
The web help may contain a number of brief tutorial videos. To play these videos, you must have Microsoft Media Player installed on your local machine. In Windows Server operating systems, you must enable the "Desktop Experience" feature using Server Manager.
Internet Explorer (or IE-rendering in other browsers) may be required for viewing video content. If using a browser other than Internet Explorer without IE rendering enabled, videos may not be visible.
InTouch OMI SDK Web Help
When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.
C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\OMISDKHelp\index.html
Start > Wonderware Documentation > InTouch OMI SDK Help
When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.
C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\OMISDKHelp\index.html
Start > Wonderware Documentation > InTouch OMI SDK Help
The following table provides guidelines for hardware configurations suitable for System Platform Version 17 software based on the size of the application. These guidelines are subject to the limitations of your Windows operating system, and if applicable, to the SQL Server edition (Express, Standard, or Enterprise). See the AVEVA GCS Technology Matrix for supported versions of Windows operating systems and SQL Server.
Application |
Level |
CPU Cores |
RAM |
HD Space |
Screen Resolution |
Network Speed |
Server Nodes: for Historian Server, Galaxy Repository (GR node), Application Server IDE, AppEngine host |
||||||
Small Application |
Minimum |
2 |
2 GB |
100 GB |
1024 x 768 |
100 Mbps |
Recommended |
4 |
4 GB |
200 GB |
1920 x 1080 |
1000 Mbps |
|
Medium Application |
Minimum |
4 |
8 GB |
200 GB |
1024 x 768 |
1000 Mbps |
Recommended |
8 |
12 GB |
500 GB |
1920 x 1080 |
1000 Mbps |
|
Large Application |
Minimum |
8 |
16 GB |
500 GB |
1024 x 768 |
1000 Mbps |
Recommended |
16 |
24 GB |
1000 GB |
1920 x 1080 |
Dual 1000 Mbps |
|
Thin Client Node |
||||||
RDP clients, ITAA, mobile devices |
Minimum |
1 |
512 MB |
N/A |
800 x 600 |
100 Mbps |
Recommended |
2 |
2 GB |
N/A |
1280 x 1024 |
100 Mbps |
|
Client Node |
||||||
WindowViewer, ViewApp, Historian Client, Remote IDE |
Minimum |
2 |
1 GB |
100 GB |
1024 x 768 |
100 Mbps |
Recommended |
4 |
4 GB |
200 GB |
1920 x 1080 |
1000 Mbps |
|
Thin Client-Server Node |
||||||
RDS, ITAA Server |
Basic RDS - Minimum |
4 |
8 GB |
200 GB |
1024 x 768 |
1000 Mbps |
Basic RDS - Recommended |
8 |
12 GB |
500 GB |
1920 x 1080 |
1000 Mbps |
|
Large RDS - Minimum |
8 |
16 GB |
500 GB |
1024 x 768 |
1000 Mbps |
|
Large RDS - Recommended |
16 |
24 GB |
1000 GB |
1920 x 1080 |
Dual 1000 Mbps |
|
All-In-One Node |
||||||
All products on a single node |
Minimum |
4 |
8 GB |
200 GB |
1280 x 1024 |
100 Mbps |
Recommended |
6 |
12 GB |
500 GB |
1920 x 1080 |
1000 Mbps |
|
Server node type applies to Historian Server, Galaxy Repository node, and nodes hosting AppEngines. |
||||||
Supported and Recommended Node Hardware Types
Product |
Server Node |
Thin Client- Server Node |
Client Node |
Thin Client |
All-In-One |
Application Server |
|||||
Galaxy Repository |
Preferred |
Supported |
Supported |
No |
Supported |
Application Engine |
Preferred |
Supported |
Supported |
No |
Supported |
IDE |
Preferred |
Supported |
Supported |
RDP |
Supported |
ViewApp Runtime |
Supported |
Supported |
Preferred |
ITAA/RDP |
Supported |
InTouch Standalone |
|||||
WindowMaker (No Modern Apps) |
Supported |
Supported |
Preferred |
RDP |
Supported |
WindowMaker (with Modern Apps) |
Preferred |
Supported |
Supported |
RDP |
Supported |
WindowViewer / InTouch ViewApp (runtime only) |
Supported |
Supported |
Preferred |
ITAA/RDP |
Supported |
InTouch for System Platform |
|||||
WindowMaker (with Managed Apps) |
Preferred |
Supported |
Supported |
RDP |
Supported |
WindowViewer / InTouch ViewApp (runtime only) |
Supported |
Supported |
Preferred |
ITAA/RDP |
Supported |
InTouch Access Anywhere |
|||||
InTouch Access Anywhere Server |
Supported |
Preferred |
No |
No |
Supported |
InTouch Access Anywhere Client (HTML5 Browser) |
Browser |
Browser |
Browser |
Browser |
Browser |
InTouch Access Anywhere Secure Gateway |
Supported |
No |
No |
No |
No |
Historian |
|||||
Historian Server |
Preferred |
Supported |
Supported |
No |
Supported |
Historian InSight Client |
Browser |
Browser |
Browser |
Browser |
Browser |
Historian Client (Active Factory) |
Supported |
Supported |
Preferred |
RDP |
Supported |
Support Components |
|||||
OI Gateway |
Preferred |
Supported |
Supported |
No |
Supported |
AVEVA Enterprise Licensing - Server |
Preferred |
Supported |
Supported |
No |
Supported |
AVEVA Enterprise Licensing - Manager |
Preferred |
Supported |
Supported |
No |
Supported |
AVEVA Enterprise Licensing - Manager Client |
Browser |
Browser |
Browser |
Browser |
Browser |
Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for Application Server 2017 Update 3. Refer to the following Microsoft Web sites for Windows and SQL Server hardware requirements.
Windows requirements
Note: System Platform 2017 Update 3 is not supported on Windows 10 versions prior to version 1607 (Anniversary update; OS build 14393).
SQL Server requirements
For system sizing examples, see the System Platform Installation Guide.
The latest product information for each System Platform product is listed in the Global Customer Support GCS Technology Matrix. Each link includes:
Minimum Required Operating System Version
The following table shows the minimum operating system for each product. See the GCS Technology Matrix for a list of all supported operating systems.
Product |
Minimum Required Operating System Version |
|
Client OS (x86 and x64) |
Server OS (x64 only) |
|
Application Server |
Windows Server 2012 (Embedded or Data Center) |
|
InTouch |
||
Historian |
||
System Platform 2017 Update 3 Web Clients
The following web clients are included with System Platform 2017 Update 3:
The client programs listed above can be used with most common web browsers. Compatible browsers include:
System Requirements by installation size
Small installation (1 to 25,000 I/O per system):
Medium installation (25,000 to 50,000 I/O per system):
Large installation (50,000 to 400,000 I/O per system):
When installing SQL Server, use the program version (32 or 64-bit) that matches the operating system.
Upgrading SQL Server with Wonderware products installed is supported.
The following virtualization software and cloud-based virtual environments are supported for System Platform 2017 Update 3:
In order to establish communication with other components and services on the network, System Platform and ArchestrA Service Bus (ASB) services require certain network ports to be opened in the Windows Firewall. Typically, these ports are automatically opened for the Windows Firewall during installation. However, if the Windows Firewall service is disabled or not running at the time of installation, or if an alternative firewall is in use, you will need to manually open the appropriate network ports in the firewall. For more information about port configuration, see "Configuring ArchestrA Service TCP Ports" in the Application Server User Guide (filename: IDE.pdf).
Due to the Data Execution Prevention (DEP) feature in Windows operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host, or will behave unpredictably in InTouch, either in WindowMaker or WindowViewer.
The ActiveX controls and error message, along with solutions to resolve the behavior, are described in detail in TechNote 522, "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)". You can download this TechNote from the AVEVA Global Customer Support (GCS) website.
The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on currently-supported Windows and Windows Server operating systems.
When InTouch WindowViewer is started and generates alarms from an interactive Windows or Windows Server desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.
This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.
To configure the AlarmViewer's alarm query
\\nodename:ip_address\intouch!$system
where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.
Windows Server 2008 R2 and later operating systems no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 R2 and later operating systems, Session 0 is no longer an interactive session, and is reserved only for Windows services. Windows Server 2008 R2 and later operating systems treat all remote connections as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.
This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session. The impact to Application Server is minimal as most Application Server processes run as services. One impact to Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.
Refer to the InTouch HMI Readme for further information about InTouch HMI applications running in the Terminal Server Console.
If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:<IP address>\InTouch!$System to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session.
NetDDE is not supported for InTouchView applications.
By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. ArchestrA Symbols make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license.
In ArchestrA Symbols, InTouch:<tagname> is still a valid method of referring to an InTouch tag on a local node.
System Platform 2017 Update 3 with InTouch HMI 2017 Update 3 supports User Account Control-enabled operations on run-time nodes.
This section describes specific behaviors and restrictions when using the supported versions of Windows and Windows Server operating systems with Application Server.
Application Server supports User Account Control-enabled operations. Starting the IDE requires elevated privileges.
Scenarios involving remote node communication fail if the Historian node is using the Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012 operating system.
For example:
Workaround:
cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
This sets LocalAccountTokenFilterPolicy registry entry value to 1. In doing so, an elevated token for the user is generated.
When the Historian Client application is running on Microsoft Windows 7, Windows Server 2008 R2, and later operating systems, User Account Control can be enabled and running as non-administrator.
IMPORTANT: System Platform 2017 Update 3 installs .NET 4.7.2 if the currently installed version of .NET is lower. If .NET 4.7.2 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to System Platform 2017 Update 3, we strongly recommended that you:
After upgrading to System Platform 2017 Update 3, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.7.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system.
System Platform 2017 Update 3 leverages the Microsoft .NET Framework 4.7.2. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. System Platform 2017 Update 3 will use .NET 4.7.2 or later.
All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.7.2 or higher. Although .NET Framework 4.7.2 is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts. These changes may also affect .NET controls developed with .NET 3.5.
In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5 and later. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:
BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());
To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:
What's New in the .NET Framework: |
http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx |
What's obsolete in the .NET Framework Class Library: |
https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx |
Migration Guide to the .NET Framework 4.7, 4.6 and 4.5: |
https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29 |
.NET Framework 4 Migration Issues: |
http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29 |
SQL Server is required for Application Server, InTouch, and Historian Server. We recommend that you install and configure the supported SQL Server version before you begin the System Platform installation program. If you select SQL Server Express during System Platform installation, it will be installed automatically (applicable to small installations only).
The System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.
Other considerations are:
If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Application Server User's Guide, "About ArchestrA User Accounts", for further information and procedures about restoring the aaAdministrators group.
For Historian Client:
For detailed installation instructions in English, see the System Platform Installation Guide (WSP_Install_Guide.pdf) or System Platform Installation Help (WSP_Install_Guide.chm). This guide supersedes the separate installation guides for the individual products. The Installation Guide pdf file is located in the root directory of the System Platform installation DVD. The Installation Help chm file is located in the InstallFiles directory of the installation DVD.
The information provided in this Readme file and the InTouch Readme file supersedes the InTouch HMI Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.
The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an ArchestrA environment. You must specify the same user account on every node when you install the System Platform components for the first time on computers that communicate with each other.
WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.
After you install a System Platform component, you can use the ArchestrA Change Network Account utility to change or re-create the ArchestrA user account. The Start menu contains a shortcut to the utility. It is under the Wonderware Utilities folder.
You must have Administrator privileges to use the Change Network Account utility. For more information, see the Change Network Account utility help
Note: If you re-create the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.
We highly recommend the following Sentinel installation and configuration sequence. For more information and details, please see “Configuring the Sentinel Agent" and "Configuring the Sentinel Manager” in the System Platform Installation Guide.
If you connect a machine to the System Management Server and then later replace the machine due to hardware failure, or restore the VM to a state prior to that connection without first disconnecting the machine from the System Management Server, you will not be able to reconnect that same machine to the System Management Server.
Cause:
To protect the security of the system, the System Management Server uniquely identifies each machine that connects to it. If an intruder attempts to pretend to be that machine (spoofing) and re-registers with that machine’s name, the System Management Server will detect the mismatched identity and reject the suspected intruder’s registration.
Solution:
After attempting to reconnect the machine, the logger will contain the warning:
“ArchestrA.CertificateManager: Please un-register the device <device name> from management server. Use the (Remove-AsbDevice) script to remove the device registration”
The PowerShell command will remove the machine’s connection information from the System Management Server. We recommend that you contact your support team, or Global Customer Support (GCS), for assistance with executing this command.
You can upgrade directly to System Platform 2017 Update 3 from System Platform 2014 R2 SP1 or later.
Upgrading is defined as installing a newer version of the software when a previous version of the software exists. An upgrade is possible when the system requirements (operating system, SQL Server, .NET Framework) are met. The upgrade process will properly remove or uninstall the previous software version and install the new version. For versions older than the current and previous licensed versions, only the latest service pack or patch versions are tested. For distributed systems, some products must be upgraded in a particular order. For more information, see upgrade information for each product in the System Platform Installation Guide.
The earliest versions of Windows that support System Platform 2017 Update 3 are:
See the GCS Technology Matrix for complete information about operating system that you can use for System Platform 2017 Update 3 products.
IMPORTANT! Back up any relevant application configuration files or databases before you start an upgrade or migration.
Once installed, a link to the AVEVA Enterprise License Manager can be found in the \AVEVA folder on the Start menu.
It can also be accessed by pointing your browser to the following URL:
http://<nodename>/AELicenseManager
where <Nodename> is localhost or the name of the node where the AVEVA Enterprise License Manager is installed.
The AVEVA Enterprise License Server can be installed separately from the AVEVA Enterprise License Manager.
In System Platform 2017 Update 3, running both InTouch HMI and InTouch OMI in a session on an RDS Server will attempt to acquire two (2) Supervisory Client Server (unlimited) licenses instead of one (1).
If you have purchased a Supervisory Client Server license (unlimited RDP sessions on a single server) and then run both InTouch HMI and InTouch OMI simultaneously, there can be issues acquiring the server license due to differences in how the license is handled between the two. The order of startup will impact the results.
This behavior is seen in only a limited number of instances, only when you have purchased a Subscription license. If you do see this behavior, change the order of InTouch HMI and InTouch OMI startup.
If this behavior continues, contact AVEVA Software Global Customer Support (GCS), describe the behavior, and request a temporary license, typically valid for 60-days.
License Reservation
Reserving a license for a specific device ensures a license will be available for that specific device whenever it is needed, regardless of the number of devices connected to the system. Keep in mind, each license can only be reserved to a single device, so if the device names are unknown ahead of time, it's better to not use reservations and instead allow the licenses to be acquired on a first-come, first-serve basis.
User-based License Reservation
In the AVEVA Enterprise License Manager license reservation page it is possible to mark a license to be reserved to a specific user. While the reservation page allows this particular configuration, it's important to know that neither InTouch OMI nor InTouch HMI ViewApps support user-based license reservations. The end-result will be the inability for the software to acquire the license reserved. Therefore, only use device-based reservations for Supervisory Client licenses.
Device-based License Reservation
When reserving a Supervisory Client license for a specific device, the Device Name needs to be the name of the computer running the InTouch HMI/OMI ViewApp. In the case where the ViewApp is running inside of a Remote Desktop Session, on an RDS (aka: Terminal Server), then the Device Name needs to follow this naming pattern:
<RDSHostName>-<RDPClientName>-<index>
where RDSHostName is the name of the Remote Desktop Server (aka: RDS or Terminal Server), and RDPClientName is the name of the PC running the RDP client software, and "index" is 1, unless there will be multiple RDP sessions from a single client machine, in which case the index should be incremented (starting at 1) for each reservation for that specific RDP client, up to the total number of RDP sessions from that specific RDP client.
Reservation Examples
Situation: A computer with a hostname of "ControlRoomA" runs InTouch OMI
Device Name: "ControlRoomA"
Situation: A computer with a hostname of "ControlRoomB" running a single Remote Desktop Client (RDP), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"
Device Name: "PrimaryRDS-ControlRoomB-1"
Situation: Two computers with hostnames "SupervisorPC1" and "LineMgrA", respectively, each running a single Remote Desktop Client (RDP) connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"
Device Names:
Situation: A computer with a hostname of "ExecutiveDesktop" running four (4) Remote Desktop Clients (RDPs), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"
Device Names:
Antivirus Software should be implemented as part of a defense-in-depth strategy to secure your Industrial Control Systems. TechNote TN2865, available from the AVEVA Global Customer Support (GCS) web site, lists important information about antivirus software. Enter your GCS credentials to access the Tech Note.
https://softwaresupportsp.schneider-electric.com/#/okmimarticle/docid/tn2865
This section documents important resolved issues broadly categorized as System Platform-level issues, and other issues in addition to those documented in the product-specific Readme files. This list is not comprehensive.
1106885 |
The Alarm Adorner for the top-level navigation item in the NavTree and/or Breadcrumb was incorrectly hidden after performing a "Switch User" operation from the Titlebar App. |
1010622 |
When the child of a custom navigation node includes a reference to an asset and the asset is undeployed, an "uncertain" Quality and Status indicator is displayed for the custom navigation node. This behavior is different than asset node behavior, which does not show Quality and Status alarms in the parent node when the asset referenced by a child node is undeployed. There is no impact to the running ViewApp and no workaround. This is simply a difference in behavior between the two types of nodes. |
1010182 |
In InTouch OMI ViewApps, touch gestures did not function the same way on slide-in panes as in the main window. |
1004542 |
Error messages were displayed in the Logger when a Galaxy was created, if a fully qualified domain name was used when adding the ArchestrA Network Account user name. |
1003341 |
In some cases, especially when font size for the navigation breadcrumb was reduced, the Alarm Adorner overlapped the down arrow symbol. |
999299 |
When an InTouch OMI ViewApp was deployed or previewed, but then the ViewApp window was closed before all panes had been populated with their contents, multiple warnings task cancellation, ArgumentOutOfRange, and failure to dispose were logged. |
1024217 |
When InTouch was configured to use the Distributed Name Manager to centralize the definition of Alarm Queries, there were some instances where the queries were not be copied over correctly during the configuration of the EAC. |
The following important known issues are listed by their assigned CR or reference number in ascending order. Additional known issues are documented in the product-specific Readme files.
796068 |
On a Galaxy Repository, uninstalling Application Server results in restoring the ArchestrA User credentials to the registry. |
804308 |
While installing System Platform 2017 on a remote node using an RDP session, you may lose your RDP connection if the Windows Firewall Service is stopped and Startup Type=Manual. If you are unable to reconnect, try the following:
|
931629 |
If a System Platform component is removed through the Control Panel ("Install/Uninstall Programs" applet), rather than by running the System Platform installation program (Setup.exe), errors messages will be logged, exception messages such as "FileNotFound" will be displayed, and Application Server deployment will no longer be successful. Workaround: Use the "Modify" workflow, as described in the System Platform Installation Guide.
|
1120630 |
A Modify operation on InBatch 2017 fails when InBatch 2017 or earlier is installed before System Platform 2017 Update 3. Workaround: Install System Platform 2017 Update 3 first, then install InBatch. |
|
|
L00123462 |
In a multi-galaxy environment, you can pair galaxies by IP address rather than using a node name (computer machine name). Unpairing galaxies identified by IP address fails when NetBIOS and DNS solutions are unavailable. Where your galaxies are identified by IP address, you must create a temporary host file to map the IP addresses as hostnames for purposes of unpairing.
|
L00123474 |
Writing from InTouch to a remote galaxy using indirect tags can fail for some of the remote references. Object Viewers on two different nodes may show different values for the same reference. You can avoid this issue by deactivating Advanced Communication Management in the IDE. Additionally, if you use the same indirect tag with scripting more than one time, you can modify your scripts to set the indirect tag's name property to an empty string after the loop completes. For example, in the following script snippet, you would add the line highlighted with bold text:
IF bRunScript THEN |
L00133534 |
Undeploying a galaxy with Object Viewer active will cause Object Viewer to shut down with an informational message that requires acknowledgement (click OK) to complete the shutdown. In a multi-galaxy configuration, with Object Viewer open, undeploying a paired Galaxy, then redeploying the galaxy without properly shutting down Object Viewer, can cause ASB services to fail to reconnect to the redeployed galaxy. To avoid this condition, click OK to shut down Object Viewer before redeploying the galaxy. |
L00139918 |
Uninstalling Wonderware InBatch versions 10.2 or 11.0 installed on a System Platform 2014R2 SP1 system results in a failure to connect to ArchestrA Service Bus (ASB) services. If you uninstall either of these InBatch versions then cannot connect to ASB services, run a repair on System Platform 2014R2 SP1 using Windows' Add/Remove Programs utility. |
L00141660 |
In a system with two GR nodes, attempting to connect from the IDE on one node to a Galaxy on the second GR node does not succeed, and the IDE shuts down. Workaround: Pair the GR nodes before trying to connect to the Galaxy on the other node. See "Working with Multiple Galaxies > Setting Up a Multi-Galaxy Environment" in the Application Server User Guide for information about configuring multi-Galaxy pairing. |
1116282 |
In a very small set of multi-galaxy (MGC) environments, communications between some System Platform subscribers and a system service they subscribe to may not be secure. In these circumstances, communications still occur, but may not be secure. If all the following elements exist in an MGC topology, communications may occur over an insecure channel:
|
1111134 1121155 |
In some circumstances, when using the Configurator to configure the System Management Server, you may be prompted to enter your user credentials. This may happen if the logged-in user does not belong to the aaAdministrators or Administrators OS group. If you are a member of either of these groups, enter your user name as DomainName\UserName. The logged-in user should be a direct member of the aaAdministrators or Administrator group. Using the credentials for a user that belongs to nested groups is not supported. That is, you cannot use credentials that belong to a group that is part of aaAdministators or Administrators. If you are not a member of aaAdministrators or Administrators on the local machine, you can obtain configuration privileges for another OS group by editing the file appsettings.json, and adding the name of the OS group to the file. The full path for this file is: To add an OS group to the file, add the new OS group after "aaAdminstrators." "AppSettings": { "AllowGroups:: [ "aaAdministrators", "insert new group name here" ] |
L00150114 |
SR59513303: TheGetCPTimeStamp() scripting method, when used in an InTouch OMI action or named script within a symbol, does not return the timestamp at run time. Instead, it returns characters for the timestamp format, such as "mm/dd/yyyy hh:mm:ss." No errors or warnings will appear in the logger. This is similar to issue 777504, documented below. Workaround: Use the GetCPTimeStamp() method in an object script instead of a symbol script. |
1100582 |
Switching languages during run time while using multi-content panes that use locale-specific scripting calls can sometimes result in errors in the logger. Workaround: Restart the ViewApp after switching the run-time language. This action fully resolves the issue with no loss of functionality. |
988079 |
If you upgrade or migrate from version 2017 or 2017 Update 1, and have an InTouch OMI ViewApp that uses the ShowGraphic scripting method, modeless windows will behave differently at run time in this version of InTouch OMI.
|
Missing NavTree |
After upgrading or migrating an InTouch OMI ViewApp from 2017 to 2017 Update 1, a warning message states that the NavTree entity could not be found. In 2017 Update 1, this navigation object has changed and is now called “NavTreeControl.” Workaround 1: To replace the NavTree object in a ViewApp or Layout when upgrading to System Platform 2017 Update 1:
Workaround 2: To replace references to NavTree when importing packages from System Platform 2017:
|
774717 |
When an InTouch OMI application (View.exe) that uses one of the following web controls is run in 4K mode or on multiple 1080p monitors, under certain circumstances the application may stop responding:
Workaround: When running a ViewApp that uses a web control on a 4K monitor, set the monitor resolution to 2560 x1440 or less. When running the ViewApp on 1080p monitors, do not attempt to span multiple monitors. |
777504 |
The GetCPQuality() scripting method is not supported in InTouch OMI. If used in a ViewApp, it always returns quality = 0 (bad quality). |
781006 |
If an invalid custom property is added to a symbol, no warning is logged in the System Management Console, even though no value is displayed for the custom property. |
781620 |
The Height and Width properties of a group with text elements do not change in accordance with changes made to the label font size, and are not rendered correctly. |
784470 |
Tooltip animations that contain multiple lines of text with line breaks may not display properly in deployed ViewApp. |
784474 |
A tooltip may partially cover the element with which it is associated in the deployed ViewApp. |
787192 |
When OSGroup security mode is used, the VerifiedWrite dialog is not displayed when you modify the value of a VerfiedWrite attribute from a combobox, if you first attempted to perform the VerifiedWrite without having the correct security credentials. |
789857 |
When an element style animation is configured with both a fill color and a blink color, the blink animation and color remain when an element style override is applied that specifies only a fill color and has the blink check box deselected. Workaround: Set the initial state without blink, then apply overrides as needed with blink enabled. |
789958 |
On some high resolution tablet devices, such as the Surface Pro 4, object names in the System Platform IDE may have insufficient line spacing between items, which can make it harder to read object names. |
794383 |
When a custom property is changed from public to private, the change does not have any affect, and the value of the private custom property is shown at run time (private values should not be shown). Similar situations occur when:
Workaround: Manually validate the outermost symbol and then deploy the ViewApp. |
797198 |
If the unfill color is set to a gradient in an Unfill animation with an animation fill style, and the fill style animation is changed, it changes the unfill color property. |
797226 |
If the expression type is set to string in the truth table for fill color animation, the fill style does not change when the value changes. |
933752 |
Starting the IDE can take up to a minute if the node on which it is running is not connected to the internet. Root Cause: To enhance security and reliability, System Platform will validate certificates. Windows then performs a check to see if the certificate has been revoked. Without an internet connection, Windows waits until the timeout for this check has been reached before allowing the IDE to start. Workaround 1 (preferred): This method changes the default timeout for the certificate check.
Workaround 2: This method disables checks for revoked certificates.
Workaround 3: This method installs the certificates that the operating system is attempting to validate onto the local machine. Once installed locally, the operating system will no longer need to access the network to retrieve them.
|
|
|
The following known issues are in addition to those documented in the InTouch Access Anywhere Readme.
L00144565 |
Installing InTouch Access Anywhere through the Modify workflow can cause various issues related to uninstalling the product at a later time. These include:
Workarounds: For issue #1 (registry keys not created), do the following:
For issue #2 (unable to launch InTouch View.exe application), do the following:
|
924302 |
When installing Historian along with any other component, and the other component requests a system restart, if you restart immediately after closing out the Configurator, a number of warnings may appear in the logger from the Historian services. This is caused by a timing issue. The warning messages can be safely ignored because they do not affect the configuration of the Historian, and do not have any effect on the system during or after the system restart. |
931966 |
When using silent install to upgrade Historian to System Platform 2017 Update 1 from a version that set a default password for SQL Server users, warning messages are logged that alert you to set new passwords for various system users after the Configurator runs. Your system will continue to operate normally without resetting the passwords, but changing the passwords will increase system security. |
779958 |
When the same license is acquired on both a local node and in an RDP session that originates from the same node, the License Manager may not show all the licenses that have been acquired. This occurs even though the licenses are counted properly on the license server. The license count that you see applies only to the node you are viewing. Thus, once you reach your maximum number of licenses, you will not be able to acquire additional licenses, even though the license manager may indicate that more licenses are available. |
793643 |
If you have not set a default browser, and you install System Platform with AVEVA Enterprise licensing selected, clicking the AVEVA Enterprise License Manager shortcut does not open the License Manager in the browser as it should. Instead, the shortcut opens in Windows Explorer. From Windows Explorer, you cannot open License Manager (the OK button is inactive). Workaround: Follow the instructions for your operating to set the default browser, and then open the AVEVA Enterprise License Manager from the shortcut, or: Open your browser and copy the shortcut link, http://localhost/AELicenseManager, directly into the browser's address bar. |
Action Icons |
Action icons in the Sentinel UI do not display correctly. Workaround: Add the Sentinel Manager IP address to the list of Trusted Sites in your browser, using one of the following formats. This is also described in the Sentinel User guide.
|
4945 |
No notification is sent when the Sentinel Agent stops reporting alerts due to too many alerts being sent. Sentinel is designed to stop sending alerts and notify the user when number of alerts coming from a single machine is abnormally high. This is done to prevent excessive resource usage. When the number of alerts has returned to normal, the Agent begins reporting alerts again. The user should receive a notification when the Agent has stopped reporting alerts. The notification does not get sent. |
5886 |
When using the Sentinel UI to add a local user that already exists in the OS, the user cannot be added and a message is displayed that the user does not exist. Workaround: Manually add the user to one of the local Sentinel user groups. The user will not appear in the list of users displayed in the UI, but will be able to log into the Sentinel Manager. |
5889 |
In Simplified Chinese, Japanese, French and German operating systems, Sentinel SQL reports are not installed and are not available in the Sentinel UI. |
5974 |
Secure SMTP email server cannot be configured silently (via command line). Workaround: The email server is configured as unsecure (HTTP) during silent install. Use the Configurator or the Sentinel UI to update the email configuration after silent installation. |
1110669 |
Following the running of the resource-intensive functions Galaxy Restore, and Galaxy Migrate and Deploy, Sentinel may issue a logger error message: ExceptionType: IndexOutofRangeExceptionMessage was outside bounds of the array. Workaround: Before running Galaxy Restore, or Galaxy Migration and Deploy, we recommend that you stop the Sentinel Agent on each Galaxy node. To stop the Sentinel Agent(s):
|
If you create a filter for a history block query that results in no matches, "Not Connected" appears in the status bar and a warning is logged to the ArchestrA Logger. The status bar should show "Connected" even though no matches are returned.
The System Platform documentation is available Adobe Acrobat .pdf files that are available from the following locations on the System Platform DVD:
InstallFiles\CD-ApplicationServer\UserDocs
InstallFiles\CD-Historian\UserDocs
InstallFiles\CD-HistorianClientUserDocs
InstallFiles\CD-Intouch\UserDocs
To view the documentation, you must first download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.
You can also access online Help systems from within the software.
This section lists important System Platform documentation corrections. For documentation corrections for individual System Platform products, see the individual product Readme files.
Item |
Location of Change |
Existing Documentation |
Change |
1 |
ArchestrA Scripting Guide (Scripting.pdf) "IF ... THEN ... ELSEIF ... ELSE ... ENDIF" section, page 112 ArchestrA IDE Help (IDE.chm) "IF ... THEN ... ELSEIF ... ELSE ... ENDIF" topic under Creating Scripts |
In the syntax description, semicolons are shown after THEN, ELSEIF, and ELSE. |
Remove the semicolons that follow THEN, ELSEIF, and ELSE. Corrected text reads: IF <Boolean_expression> THEN [statements]; [ { ELSEIF [statements] } ]; [ ELSE [statements] ]; ENDIF; |
Last revision: 12/18/2018
This Readme provides information about Wonderware InTouch Access Anywhere Update 3, Version 17.3.000.
InTouch Access Anywhere™ provides remote access to InTouch™ applications with an HTML5 Web browser running on a desktop computer or a mobile device. Any Web browser that supports HTML5 can be used as the client to view InTouch applications running on a remote desktop server. InTouch Access Anywhere enables you to select an InTouch application from a list and view it running in WindowViewer.
The InTouch Access Anywhere installation media provides the following:
This section summarizes InTouch Access Anywhere installation requirements, supported browsers, and considerations for viewing InTouch applications on mobile devices. For more detailed information, see the Wonderware InTouch Access Anywhere Documentation
The following list describes the prerequisites to install the InTouch Access Anywhere Server or Secure Gateway.
Important: All existing instances of InTouch Access Anywhere components must be removed from the computer before installing Update 3. Earlier versions of InTouch Access Anywhere Servers cannot be modified or repaired using Update 3.
Note: Windows 10 does not support .NET 4.5.2. .NET 4.6.2 and later must be installed for Windows 10 support.
Note: If you are installing InTouch Access Anywhere from System Platform 2017 Update 3, the installer verifies the current, installed versions of .NET on the computer. When only earlier versions of .NET are detected,the installer automatically updates the computer to .NET 4.7.2.
Per-Device RDS licenses are not supported.
Important Security Requirement: Securely Deploying InTouch Access Anywhere
Direct access to the InTouch Access Anywhere Secure Gateway over the Internet is not supported. Accessing the Secure Gateway by means of a VPN tunnel for all remote connections is recommended.
InTouch Access Anywhere can be accessed from smart phones, tablets, and laptop computers that provide an HTML5-compliant web browser.
Browsers Tested with InTouch Access Anywhere
Browsers verified to work with InTouch Access Anywhere include the following:
Important: Only the browser versions listed above have been tested on the specified hardware platforms (PCs, tablets and Smart Phones). No testing has been done on HTML5 browsers running on other devices not included in the list shown above (SmartTVs, eBook Readers, or game consoles).
Functionally Compatible Browsers
Certain versions of the browsers listed above, such as:
are in theory functionally compatible with InTouch Access Anywhere. While you may be able to use these versions of the web browsers with InTouch Access Anywhere, specific behaviors are unknown because no formal testing has been conducted.
Browsers: Important Notes
Although Wonderware InTouch Access Anywhere supports the listed browsers, you should review the Known Issues and Behaviors section of this Readme for issues specific to each browser.
Run-time interactions with InTouch applications are different on mobile devices than on traditional desktop computers. For example:
When using InTouch Access Anywhere to remotely view and interact with your applications, it is important to be aware of the behavior differences among devices, operating systems, and browsers. For the best user experience, you should become familiar with the touch interfaces in the devices you will use, and factor these differences into the design of your InTouch applications. For example:
This section lists defects resolved with this release of InTouch Access Anywhere.
Defect Number |
Description |
L00150532 |
The Display setting 'Open browser links on client (URL redirection)' did not work as expected. |
This section describes known issues and platform/browser-specific behaviors in InTouch Access Anywhere. The issues are grouped by areas affected by the issue. Workarounds are provided when available. You can also refer to the InTouch Access Anywhere user documentation for more information.
Wonderware InTouch Access Anywhere product documentation is provided as a set of Portable Document Files (PDF), which are located at the root of CD installation disc.
InTouch Access Anywhere Product Documentation Name |
File Name |
Wonderware InTouch Access Anywhere User Guide |
ITAA_UserManual.pdf |
Wonderware InTouch Access Anywhere Server Administrator Manual |
ITAA_Server_AdminManual.pdf |
Wonderware InTouch Access Anywhere Secure Gateway Administrator Manual |
ITAA_Gateway_AdminManual.pdf |
You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.
After installing Adobe Reader, double-click a PDF file with your pointing device to view the book with Adobe Reader. You can also open a PDF with the Adobe Reader Open command from the File menu.
|
Copyright © 2018 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |